In response to this:

We're seeing CI fail because we don't set terminationMessagePolicy: FallbackToLogsOnError

This fixes how we deploy the external CCM for aws.

See https://redhat.atlassian.net/browse/OCPBUGS-84512 for additional context.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

❌ Failed checks (1 warning)

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

Comment: /pj-rehearse to run up to 5 rehearsals
Comment: /pj-rehearse skip to opt-out of rehearsals
Comment: /pj-rehearse {test-name}, with each test separated by a space, to run one or more specific rehearsals
Comment: /pj-rehearse more to run up to 10 rehearsals
Comment: /pj-rehearse max to run up to 25 rehearsals
Comment: /pj-rehearse auto-ack to run up to 5 rehearsals, and add the rehearsals-ack label on success
Comment: /pj-rehearse list to get an up-to-date list of affected jobs
Comment: /pj-rehearse abort to abort all active rehearsals
Comment: /pj-rehearse network-access-allowed to allow rehearsals of tests that have the restrict_network_access field set to false. This must be executed by an openshift org member who is not the PR author

Once you are satisfied with the results of the rehearsals, comment: /pj-rehearse ack to unblock merge. When the rehearsals-ack label is present on your PR, merge will no longer be blocked by rehearsals.
If you would like the rehearsals-ack label removed, comment: /pj-rehearse reject to re-block merging.

• ci-operator/step-registry/platform-external/OWNERS [elmiko]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

• bug is open, matching expected state (open)
• bug target version (5.0.0) matches configured target version for branch (5.0.0)
• bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, POST)

In response to this:

/jira refresh

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

In response to this:

We're seeing CI fail because we don't set terminationMessagePolicy: FallbackToLogsOnError

This fixes how we deploy the external CCM for aws.

See https://redhat.atlassian.net/browse/OCPBUGS-84512 for additional context.

Summary by CodeRabbit

This PR updates the OpenShift CI infrastructure configuration for the AWS external Cloud Controller Manager (CCM) deployment. Specifically, it adds the terminationMessagePolicy: FallbackToLogsOnError setting to the container specification in the CCM deployment manifest generated by the step registry script.

The change addresses CI failures by ensuring that container termination messages are properly captured in logs when the external CCM pod terminates. The modification is minimal—a single line addition to the deployment configuration script—and does not alter any other manifest content or control flow logic.

File changed:

• ci-operator/step-registry/platform-external/ccm/conf/aws/platform-external-ccm-conf-aws-commands.sh (+1 line)

This is an infrastructure-focused change that improves the reliability and debuggability of the external CCM deployment on OpenShift clusters using AWS.

Note: The PR references Jira issue OCPBUGS-84512, which the CI bot flagged as lacking a target version assignment (expected "5.0.0"). The validation warning does not block the PR, but the underlying Jira issue may need to be updated with the appropriate version targeting.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.